Systems and methods of verifying origin of request for payment

ABSTRACT

A method for verifying origin of request for payments may include a financial institution computer program: receiving a request for a payment URL from a merchant, the payment URL provided for a transaction with a customer; generating the payment URL, wherein the payment URL comprises a pointer to a network location for the financial institution; providing the payment URL to a customer electronic device; receiving, from the customer electronic device and at a browsed URL, a stored or pinned certificate of domain for the payment URL; (5) comparing the stored or pinned certificate of domain for the payment URL to a certificate of domain for the browsed URL; presenting a payment page in response to a match; and returning an error in response to a mismatch.

BACKGROUND OF THE INVENTION 1. Field of the Invention

Embodiments relate generally to systems and methods for verifying originof request for payment.

2. Description of the Related Art

Customers may be presented with the opportunity to receive a messagethat allows them to make a payment to merchant. When the customerreceives such message, the customer may make the payment from thecustomer’s own device by navigating to the URL that accepts payments.The customer, however, does not know anything about the URL - it couldbe a valid URL, or it could be a link that causes payment to be made toa malicious party.

SUMMARY OF THE INVENTION

Systems and methods for verifying origin of request for payment aredisclosed. In one embodiment, a method for verifying origin of requestfor payments may include: (1) receiving, by a financial institutioncomputer program executed by a financial institution backend for afinancial institution, a request for a payment URL from a merchant, thepayment URL provided for a transaction with a customer using a customerelectronic device; (2) generating, by the financial institution computerprogram, the payment URL, wherein the payment URL comprises a pointer toa network location for the financial institution; (3) providing, by thefinancial institution computer program, the payment URL to the customerelectronic device; (4) receiving, by the financial institution computerprogram and from an application executed by the customer electronicdevice and at a browsed URL, a stored or pinned certificate of domainfor the payment URL; (5) comparing, by the financial institutioncomputer program, the stored or pinned certificate of domain for thepayment URL to a certificate of domain for the browsed URL; (6)presenting, by the financial institution computer program, a paymentpage in response to the certificate of domain for the payment URLmatching the stored or pinned certificate of domain for the payment URL;and (7) returning, by the financial institution computer program, anerror in response to the certificate of domain for the payment URL notmatching the stored or pinned certificate of domain for the payment URL.

In one embodiment, the payment URL may also include a session identifieror a global unique identifier.

In one embodiment, the application executed by the customer electronicdevice may include a computer program or a browser application.

In one embodiment, the payment URL may be communicated by shortmessaging service (SMS) or email.

In one embodiment, the method may also include: receiving, at thepayment page, payment details from the customer electronic device;executing, by the financial institution computer program, thetransaction using the payment details; and crediting, by the financialinstitution computer program, a merchant account for payment.

In one embodiment, the error may also include a fraud message.

According to another embodiment, a method for verifying origin ofrequest for payment using a centralized payment application may include:(1) receiving, at a centralized payment application backend executed bya centralized payment backend, a certificate of domain for a payment URLfrom a plurality of financial institution backends, each financialinstitution backend associated with one or more merchant; (2)communicating, by the centralized payment application backend, thecertificates of domain for the payment URLs to a centralized paymentapplication executed by a customer electronic device, wherein thecentralized payment application stores or pins the certificates ofdomain for the payment URLs; (3) receiving, from the centralized paymentapplication and at a browsed URL, a certificate of domain for one of thepayment URLs; (4) comparing, by the centralized payment applicationbackend, the certificate of domain for the browsed URL to one of thestored or pinned certificates of domain for the payment URL; (5)presenting, by the centralized payment application backend, a paymentpage in response to the received certificate of domain matching thestored or pinned certificate of domain; and (6) returning, by thecentralized payment application backend, an error in response to thereceived certificate of domain not matching the stored or pinnedcertificate of domain.

In one embodiment, the payment URL may also include a session identifieror a global unique identifier.

In one embodiment, the centralized payment application executed by thecustomer electronic device may include a centralized payment computerprogram or a browser application.

In one embodiment, the payment URL may be communicated by shortmessaging service (SMS) or email.

In one embodiment, the method may also include: receiving, at thepayment page, payment details from the customer electronic device;executing, by the financial institution computer program, thetransaction using the payment details; and crediting, by the financialinstitution computer program, a merchant account for payment.

In one embodiment, the error may also include a fraud message.

In one embodiment, the payment URL may be displayed at a paymentterminal.

According to another embodiment, an electronic device may include: amemory storing a financial institution computer program; and a computerprocessor. When executed by the computer processor, the financialinstitution computer program may cause the computer processor to:receive a request for a payment URL from a merchant, the payment URLprovided for a transaction with a customer using a customer electronicdevice; generate the payment URL, wherein the payment URL comprises apointer to a network location for the financial institution; provide thepayment URL to the customer electronic device; receive from anapplication executed by the customer electronic device and at a browsedURL, a stored or pinned certificate of domain for the payment URL;compare the stored or pinned certificate of domain for the payment URLto a certificate of domain for the browsed URL; present a payment pagein response to the certificate of domain for the payment URL matchingthe stored or pinned certificate of domain for the payment URL; andreturn an error in response to the certificate of domain for the paymentURL not matching the stored or pinned certificate of domain for thepayment URL.

In one embodiment, the payment URL may also include a session identifieror a global unique identifier.

In one embodiment, the application executed by the customer electronicdevice may include a computer program or a browser application.

In one embodiment, the payment URL may be communicated by shortmessaging service (SMS) or email.

In one embodiment, the financial institution computer program may alsocause the computer processor to: receive payment details from thecustomer electronic device; execute the transaction using the paymentdetails; and credit a merchant account for payment.

In one embodiment, the error may also include a fraud message.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to facilitate a fuller understanding of the present invention,reference is now made to the attached drawings. The drawings should notbe construed as limiting the present invention but are intended only toillustrate different aspects and embodiments.

FIG. 1 is a depicts a system for verifying origin of request for paymentaccording to an embodiment;

FIG. 2 depicts a method for verifying origin of request for paymentaccording to an embodiment;

FIG. 3 depicts a system for verifying origin of request for paymentusing a centralized payment application according to an embodiment;

FIG. 4 depicts a method for verifying origin of request for paymentusing a centralized payment application according to an embodiment;

FIG. 5 depicts a system for verifying origin of request for paymentusing a centralized payment application according to another embodiment;and

FIG. 6 depicts a method for verifying origin of request for paymentusing a centralized payment application according to another embodiment.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments relate generally to systems and methods for verifying originof request for payment.

In embodiments, a trusted application provided by a financialinstitution or a centralized service may pin or embed the paymentdomain’s X.509 certificate in the application. The trusted app may bedeep linked to open a URL, so that when the user clicks the URL, theoperating system (OS) on the customer’s electronic device may recognizethat clicked link is associated with a trusted installed application.The OS may launch the installed application to access the payment URL,and the trusted application may match the embedded certificate with thecertificate detected in URL that was used to open the trustedapplication. If a match is successful, the trusted application mayrender a payment page where user may select or enter the cardinformation to make the payment. If the match is unsuccessful, thetrusted application may inform the user that the link is potentiallyfraudulent.

Referring to FIG. 1 , a system for verifying origin of request forpayment according to an embodiment. System 100 may include electronicdevice 110, which may be any suitable customer electronic deviceincluding computers (e.g., desktop, notebook, laptop, tablet, etc.),smartphones and smart devices, Internet of Things (IoT) devices, etc.Electronic device 110 may execute one or more computer applications orprograms, such as financial institution application 112, browser ormerchant application 114, etc.

Financial institution 120 may be a financial institution that is used bymerchant 130 or holds one or more account for merchant 130. In oneembodiment, financial institution 120 may provide financial institutionbackend 122 that may be any suitable electronic device (e.g., physicalservers, cloud servers, combinations, etc.). Backend 122 may executefinancial institution computer program 124 that may interface withfinancial institution application 112.

Merchant 130 may provide goods or services for customer 115. Merchant130 may provide merchant backend 132 that may be any suitable electronicdevice (e.g., physical servers, cloud servers, combinations, etc.).Backend 132 may execute merchant computer program 134 that may interfacewith browser or merchant application 114.

Referring to FIG. 2 , a method for verifying origin of request forpayment according to an embodiment. In step 205, using a customerelectronic device, such as a smartphone executing a merchant applicationor a browser application, a customer may make a purchase at merchantwebsite.

In step 210, a computer program executed by a computer at the merchantmay request that the merchant’s financial institution generate a paymentURL for the transaction with the customer.

In step 215, a computer program executed by a backend for the financialinstitution may generate a payment URL and may provide the payment URLto the customer electronic device. In one embodiment, the payment URLmay include a pointer to a network location for the financialinstitution. In one embodiment, the computer program may further providea reference to the transaction or a representation of the purchase. Inone embodiment, in terms of data, the link may be generic to increasesecurity, and the pointer may be based on a session identifier, a globalunique identifier (GUID), etc.

In one embodiment, the payment URL may be sent by short messagingservice (SMS), email, in-app notification, etc.

In step 220, the customer may open the payment URL, which may launch anapplication provided by the financial institution. In one embodiment, ifthe application is not present on the customer electronic device, thecustomer may be prompted to download the application.

The financial institution application may store or pin a certificate ofdomain for the payment URL that may be used to validate the payment URL,and the application may provide the stored or pinned certificate ofdomain for the payment URL to the computer program executed at thefinancial institution backend.

In step 225, the computer program executed at the financial institutionbackend may compare and validate the certificate of domain for thepayment URL with the stored or pinned certificate for the payment URLfrom the financial institution application.

In step 230, if the certificate of domain for the browsed payment URLmatches the stored or pinned certificate of domain for the payment URL,in step 235, the financial institution application may present a paymentpage for the customer to make a payment to merchant.

In step 240, the customer may select a payment mechanism from thecustomer’s wallet (e.g., credit card, debit card, account, etc.) or mayenter the card details manually. In step 245, the financial institutionmay receive the selection and may submit payment to a merchant bankaccount. For example, the financial institution may execute thetransaction using the payment details and credit a merchant account forpayment.

If there is a mismatch, which indicates that the link may be fraudulent,in step 250, the financial institution application may return an errorand may present the error to the customer.

Referring to FIG. 3 , a system for verifying origin of request forpayment using a centralized payment application according to anembodiment. System 300 may include electronic device 310, which may beany suitable customer electronic device including computers (e.g., adesktop, notebook, laptop, tablet, etc.), smartphones and smart devices,Internet of Things (IoT) devices, etc. Electronic device 310 may executeone or more computer applications or programs, such as centralizedpayment application 312, browser or merchant application 314, etc.

Financial institution 320 may be a financial institution that is used byone or more merchant 330 or holds one or more account for merchants 330.In one embodiment, financial institution 320 may provide financialinstitution backend 322 that may be any suitable electronic device(e.g., physical servers, cloud servers, combinations, etc.).

In one embodiment, a plurality of financial institutions 320 may beprovided as is necessary and/or desired.

Merchant 330 may provide goods or services for customer 315. Merchant330 may provide merchant backend 132 that may be any suitable electronicdevice (e.g., physical servers, cloud servers, combinations, etc.).Backend 332 may execute merchant computer program 334 that may interfacewith browser or merchant application 314.

Although only one merchant 330 is depicted in FIG. 3 , it should berecognized that a plurality of merchants 330 may be included. Inaddition, each merchant 330 may be associated with a financialinstitution 320. In embodiments, more than one merchant 330 may beassociated with the same financial institution 320.

System 300 may further include centralized payment application host 340,which may be any suitable trusted entity, including financialinstitutions, FinTechs, third parties, etc. Centralized paymentapplication host 340 may provide centralized payment application backend342, which may be any suitable electronic device (e.g., physicalservers, cloud servers, combinations, etc.). Centralized paymentapplication backend 342 may interface with merchant backend 332.

Centralized payment application host 340 may execute centralized paymentapplication 344 that may interface with browser or centralized paymentapplication 312.

In one embodiment, centralized payment application host 340 may be oneof financial institutions 320.

Referring to FIG. 4 , a method for verifying origin of request forpayment using a centralized payment application according to anembodiment

In step 405, one or more merchant financial institution backends mayprovide certificates of domain for payment URLs to a centralized paymentapplication backend. Each financial institution may have its own paymentURL. The centralized payment application backend may communicate thecertificates to a centralized payment application executed on a customerelectronic device, which may store or pin the certificates in thecentralized payment application.

In step 410, using a customer electronic device, such as a smartphoneexecuting a merchant application or a browser application, a customermay make a purchase at merchant website.

In step 415, a computer program executed by a computer at the merchantmay request that the merchant’s financial institution generate a paymentURL for the customer.

In step 420, a computer program executed by a backend for the financialinstitution may generate a payment URL and may provide the payment URLto the customer electronic device. In one embodiment, the payment URLmay include a pointer to a network location for the financialinstitution, a session identifier, a GUID, etc.

In one embodiment, the payment URL may be sent by SMS, email, in-appnotification, etc.

In step 425, the customer may open the payment URL, which may launch anapplication provided by the centralized payment application host. In oneembodiment, if the centralized payment application is not present on thecustomer electronic device, the customer may be prompted to download thecentralized payment application.

The centralized payment application may provide the stored or pinnedcertificate of domain for the payment URL to the computer programexecuted at the centralized payment application backend.

In step 430, the centralized payment application backend may compare andvalidate the certificate of domain with the pinned or stored certificateof domain from the centralized payment application.

In step 435, if there is a match, in step 440, the centralized paymentapplication presents payment page for customer to make payment tomerchant. In step 445, the customer may select a card or account from awallet in the payment application or may enter the details manually. Instep 450, the centralized payment application may submit payment to themerchant bank account.

If there is a mismatch, which indicates that the link may be fraudulent,in step 455, the centralized payment application may return an error andmay present the error to the customer.

Referring to FIG. 5 , a system for verifying origin of request forpayment using a centralized payment application is disclosed accordingto another embodiment. System 500 may include electronic device 510,which may be any suitable customer electronic device including computers(e.g., desktop, notebook, laptop, tablet, etc.), smartphones and smartdevices, Internet of Things (IoT) devices, etc. Electronic device 510may execute one or more computer applications or programs, such ascentralized payment application 512.

Financial institution 520 may be a financial institution that is used byone or more merchant 530 or holds one or more account for merchants 530.In one embodiment, financial institution 520 may provide financialinstitution backend 522 that may be any suitable electronic device(e.g., physical servers, cloud servers, combinations, etc.). A pluralityof financial institutions 520 may be provided.

Merchant 530 may provide goods or services for customer 515. Merchant530 may provide merchant backend 532 that may be any suitable electronicdevice (e.g., physical servers, cloud servers, combinations, etc.).Backend 532 may interface with financial institution backend 522.

Merchant 530 may provide point of sale device 534, which may be astand-alone point of sale device, a point of sale application executedon a suitable electronic device, etc. Point of sale device 534 mayreceive and display machine readable code 536 that may be provided byfinancial institution backend 522. In one embodiment, machine readablecode 536 may be a sticker that may be affixed to or near point of saledevice 534; in another embodiment, machine readable code 536 may bedisplayed by a display on point of sale device 534.

Although only one merchant 530 is depicted in FIG. 5 , it should berecognized that a plurality of merchants 530 may be included. Inaddition, each merchant 530 may be associated with a financialinstitution 520. In embodiments, more than one merchant 530 may beassociated with the same financial institution 520.

Machine readable code 536 may include a URL that may point to thefinancial institution 520 associated with the merchant. In oneembodiment, the URL may be generated by centralized payment applicationbackend 542.

System 500 may further include centralized payment application host 540,which may be any suitable trusted entity, including financialinstitutions, FinTechs, third parties, etc. Centralized paymentapplication host 540 may provide centralized payment application backend542, which may be any suitable electronic device (e.g., physicalservers, cloud servers, combinations, etc.). Centralized paymentapplication backend 542 may interface with merchant backend 532.

Centralized payment application host 540 may execute centralized paymentapplication 544 that may interface with a browser or centralized paymentapplication 512.

In one embodiment, centralized payment application host 540 may be oneof financial institutions 520.

Referring to FIG. 6 , a method for verifying origin of request forpayment using a centralized payment application is disclosed accordingto another embodiment.

In step 605, one or more financial institutions may provide certificatesof domain for payment URLs to a centralized payment application. In step610, each financial institution may further provide a machine-readablecode with an embedded URL to a POS device provided at the merchant. Themachine-readable code may be provided as a sticker, as an image, etc.

In step 615, a customer may scan the machine-readable code to makepayment at merchant POS device. In one embodiment, the customer may scanthe machine-readable code with the centralized payment application, ormay scan the code with an image capture application.

In step 620, the electronic device may launch the centralized paymentapplication if not already launched, or may prompt the customer todownload the centralized payment application. The centralized paymentapplication may open the URL from the machine-readable code.

The centralized payment application may provide the stored or pinnedcertificate of domain for the payment URL to the computer programexecuted at the centralized payment application backend.

In step 625, the centralized payment application backend may compare andvalidate the certificate of domain of the URL with the stored or pinnedcertificate from the centralized payment application.

In step 630, if there is a match, in step 635, the centralized paymentapplication may present a payment page for customer to make payment tomerchant. In step 640, the customer may select a card or account from awallet in the payment application or may enter the details manually. Instep 645, the centralized payment application may submit payment to themerchant bank account.

If there is a mismatch, which indicates that the link may be fraudulent,in step 650, the centralized payment application may return an error andmay present the error to the customer.

Although multiple embodiments have been described, it should berecognized that these embodiments are not exclusive to each other, andthat features from one embodiment may be used with others.

Hereinafter, general aspects of implementation of the systems andmethods of the invention will be described.

The system of the invention or portions of the system of the inventionmay be in the form of a “processing machine,” such as a general-purposecomputer, for example. As used herein, the term “processing machine” isto be understood to include at least one processor that uses at leastone memory. The at least one memory stores a set of instructions. Theinstructions may be either permanently or temporarily stored in thememory or memories of the processing machine. The processor executes theinstructions that are stored in the memory or memories in order toprocess data. The set of instructions may include various instructionsthat perform a particular task or tasks, such as those tasks describedabove. Such a set of instructions for performing a particular task maybe characterized as a program, software program, or simply software.

In one embodiment, the processing machine may be a specializedprocessor.

As noted above, the processing machine executes the instructions thatare stored in the memory or memories to process data. This processing ofdata may be in response to commands by a user or users of the processingmachine, in response to previous processing, in response to a request byanother processing machine and/or any other input, for example.

As noted above, the processing machine used to implement the inventionmay be a general-purpose computer. However, the processing machinedescribed above may also utilize any of a wide variety of othertechnologies including a special purpose computer, a computer systemincluding, for example, a microcomputer, mini-computer or mainframe, aprogrammed microprocessor, a micro-controller, a peripheral integratedcircuit element, a CSIC (Customer Specific Integrated Circuit) or ASIC(Application Specific Integrated Circuit) or other integrated circuit, alogic circuit, a digital signal processor, a programmable logic devicesuch as a FPGA, PLD, PLA or PAL, or any other device or arrangement ofdevices that is capable of implementing the steps of the processes ofthe invention.

The processing machine used to implement the invention may utilize asuitable operating system.

It is appreciated that in order to practice the method of the inventionas described above, it is not necessary that the processors and/or thememories of the processing machine be physically located in the samegeographical place. That is, each of the processors and the memoriesused by the processing machine may be located in geographically distinctlocations and connected so as to communicate in any suitable manner.Additionally, it is appreciated that each of the processor and/or thememory may be composed of different physical pieces of equipment.Accordingly, it is not necessary that the processor be one single pieceof equipment in one location and that the memory be another single pieceof equipment in another location. That is, it is contemplated that theprocessor may be two pieces of equipment in two different physicallocations. The two distinct pieces of equipment may be connected in anysuitable manner. Additionally, the memory may include two or moreportions of memory in two or more physical locations.

To explain further, processing, as described above, is performed byvarious components and various memories. However, it is appreciated thatthe processing performed by two distinct components as described abovemay, in accordance with a further embodiment of the invention, beperformed by a single component. Further, the processing performed byone distinct component as described above may be performed by twodistinct components. In a similar manner, the memory storage performedby two distinct memory portions as described above may, in accordancewith a further embodiment of the invention, be performed by a singlememory portion. Further, the memory storage performed by one distinctmemory portion as described above may be performed by two memoryportions.

Further, various technologies may be used to provide communicationbetween the various processors and/or memories, as well as to allow theprocessors and/or the memories of the invention to communicate with anyother entity; i.e., so as to obtain further instructions or to accessand use remote memory stores, for example. Such technologies used toprovide such communication might include a network, the Internet,Intranet, Extranet, LAN, an Ethernet, wireless communication via celltower or satellite, or any client server system that providescommunication, for example. Such communications technologies may use anysuitable protocol such as TCP/IP, UDP, or OSI, for example.

As described above, a set of instructions may be used in the processingof the invention. The set of instructions may be in the form of aprogram or software. The software may be in the form of system softwareor application software, for example. The software might also be in theform of a collection of separate programs, a program module within alarger program, or a portion of a program module, for example. Thesoftware used might also include modular programming in the form ofobject-oriented programming. The software tells the processing machinewhat to do with the data being processed.

Further, it is appreciated that the instructions or set of instructionsused in the implementation and operation of the invention may be in asuitable form such that the processing machine may read theinstructions. For example, the instructions that form a program may bein the form of a suitable programming language, which is converted tomachine language or object code to allow the processor or processors toread the instructions. That is, written lines of programming code orsource code, in a particular programming language, are converted tomachine language using a compiler, assembler or interpreter. The machinelanguage is binary coded machine instructions that are specific to aparticular type of processing machine, i.e., to a particular type ofcomputer, for example. The computer understands the machine language.

Any suitable programming language may be used in accordance with thevarious embodiments of the invention. Also, the instructions and/or dataused in the practice of the invention may utilize any compression orencryption technique or algorithm, as may be desired. An encryptionmodule might be used to encrypt data. Further, files or other data maybe decrypted using a suitable decryption module, for example.

As described above, the invention may illustratively be embodied in theform of a processing machine, including a computer or computer system,for example, that includes at least one memory. It is to be appreciatedthat the set of instructions, i.e., the software for example, thatenables the computer operating system to perform the operationsdescribed above may be contained on any of a wide variety of media ormedium, as desired. Further, the data that is processed by the set ofinstructions might also be contained on any of a wide variety of mediaor medium. That is, the particular medium, i.e., the memory in theprocessing machine, utilized to hold the set of instructions and/or thedata used in the invention may take on any of a variety of physicalforms or transmissions, for example. Illustratively, the medium may bein the form of paper, paper transparencies, a compact disk, a DVD, anintegrated circuit, a hard disk, a floppy disk, an optical disk, amagnetic tape, a RAM, a ROM, a PROM, an EPROM, a wire, a cable, a fiber,a communications channel, a satellite transmission, a memory card, a SIMcard, or other remote transmission, as well as any other medium orsource of data that may be read by the processors of the invention.

Further, the memory or memories used in the processing machine thatimplements the invention may be in any of a wide variety of forms toallow the memory to hold instructions, data, or other information, as isdesired. Thus, the memory might be in the form of a database to holddata. The database might use any desired arrangement of files such as aflat file arrangement or a relational database arrangement, for example.

In the system and method of the invention, a variety of “userinterfaces” may be utilized to allow a user to interface with theprocessing machine or machines that are used to implement the invention.As used herein, a user interface includes any hardware, software, orcombination of hardware and software used by the processing machine thatallows a user to interact with the processing machine. A user interfacemay be in the form of a dialogue screen for example. A user interfacemay also include any of a mouse, touch screen, keyboard, keypad, voicereader, voice recognizer, dialogue screen, menu box, list, checkbox,toggle switch, a pushbutton or any other device that allows a user toreceive information regarding the operation of the processing machine asit processes a set of instructions and/or provides the processingmachine with information. Accordingly, the user interface is any devicethat provides communication between a user and a processing machine. Theinformation provided by the user to the processing machine through theuser interface may be in the form of a command, a selection of data, orsome other input, for example.

As discussed above, a user interface is utilized by the processingmachine that performs a set of instructions such that the processingmachine processes data for a user. The user interface is typically usedby the processing machine for interacting with a user either to conveyinformation or receive information from the user. However, it should beappreciated that in accordance with some embodiments of the system andmethod of the invention, it is not necessary that a human user actuallyinteract with a user interface used by the processing machine of theinvention. Rather, it is also contemplated that the user interface ofthe invention might interact, i.e., convey and receive information, withanother processing machine, rather than a human user. Accordingly, theother processing machine might be characterized as a user. Further, itis contemplated that a user interface utilized in the system and methodof the invention may interact partially with another processing machineor processing machines, while also interacting partially with a humanuser.

It will be readily understood by those persons skilled in the art thatthe present invention is susceptible to broad utility and application.Many embodiments and adaptations of the present invention other thanthose herein described, as well as many variations, modifications andequivalent arrangements, will be apparent from or reasonably suggestedby the present invention and foregoing description thereof, withoutdeparting from the substance or scope of the invention.

Accordingly, while the present invention has been described here indetail in relation to its exemplary embodiments, it is to be understoodthat this disclosure is only illustrative and exemplary of the presentinvention and is made to provide an enabling disclosure of theinvention. Accordingly, the foregoing disclosure is not intended to beconstrued or to limit the present invention or otherwise to exclude anyother such embodiments, adaptations, variations, modifications orequivalent arrangements.

1. A method for verifying an origin of request for payments, comprising:receiving, by a financial institution computer program executed by afinancial institution backend for a financial institution, a request,wherein: the request is for a payment URL; and the request is receivedfrom a merchant; generating, by the financial institution computerprogram, the payment URL, wherein: the payment URL comprises a pointerto a network location for the financial institution; the payment URL isassociated with a transaction made by a customer of the financialinstitution using a customer electronic device; the payment URLcomprises a payment domain maintained by the financial institution; andthe financial institution computer program maintains a certificate ofdomain for the payment domain; providing, by the financial institutioncomputer program, the payment URL to the customer electronic device;receiving, by the financial institution computer program and from anapplication executed by the customer electronic device, a storedcertificate, wherein: the stored certificate is stored by theapplication executed by the customer electronic device on the customerelectronic device; and the stored certificate is sent by the applicationexecuted by the customer electronic device to the financial institutioncomputer program in response to the customer activating the payment URL;comparing, by the financial institution computer program, the storedcertificate to the certificate of domain for the payment domain; andpresenting, by the financial institution computer program, a paymentpage in response to the certificate of domain for the payment domainmatching the stored certificate.
 2. The method of claim 1, wherein thepayment URL further comprises a session identifier or a global uniqueidentifier.
 3. The method of claim 1, wherein the application executedby the customer electronic device comprises a computer program or abrowser application.
 4. The method of claim 1, wherein the payment URLis communicated by short messaging service (SMS) or email.
 5. The methodof claim 1, further comprising: receiving, at the payment page, paymentdetails from the customer electronic device; executing, by the financialinstitution computer program, the transaction using the payment details;and crediting, by the financial institution computer program, a merchantaccount for payment. 6-13. (canceled)
 14. An electronic device,comprising: a memory storing a financial institution computer program;and a computer processor; wherein, when executed by the computerprocessor, the financial institution computer program causes thecomputer processor to: receive a request wherein: the request is for apayment URL; and the request is received from a merchant; generate thepayment URL, wherein: the payment URL comprises a pointer to a networklocation for the financial institution; the payment URL is associatedwith a transaction made by a customer of the financial institution usinga customer electronic device; the payment URL comprises a payment domainmaintained by the financial institution; and the financial institutioncomputer program maintains a certificate of domain for the paymentdomain; provide the payment URL to the customer electronic device;receive from an application executed by the customer electronic device,a stored certificate; wherein: the stored certificate is stored by theapplication executed by the customer electronic device on the customerelectronic device; and the stored certificate is sent by the applicationexecuted by the customer electronic device to the financial institutioncomputer program in response to the customer activating the payment URL;compare the stored certificate to the certificate of domain for thepayment domain browsed; present a payment page in response to thecertificate of domain for the payment domain matching the storedcertificate .
 15. The electronic device of claim 14, wherein the paymentURL further comprises a session identifier or a global uniqueidentifier.
 16. The electronic device of claim 14, wherein theapplication executed by the customer electronic device comprises acomputer program or a browser application.
 17. The electronic device ofclaim 14, wherein the payment URL is communicated by short messagingservice (SMS) or email.
 18. The electronic device of claim 14, whereinthe financial institution computer program further causes the computerprocessor to: receive payment details from the customer electronicdevice; execute the transaction using the payment details; and credit amerchant account for payment.
 19. (canceled)